Skip to main content

Limitations and notes

The things worth knowing before you commit a design to a customer's site.

Choosing an icon​

The setup app shows the real Crestron glyphs in a searchable, grouped picker — pick the one you want and it appears on the control. A small number of the more obscure icon names have no preview in the app and show as a name chip instead; they still render correctly on the tile. If a name is not a valid Crestron icon the app flags it, because it would otherwise draw blank on the tile.

Outbound requests are bounded​

  • A request times out after at most 30 seconds (10 by default) — a tile must never hang on a slow endpoint. If a device legitimately takes longer than that to respond, it is not something a button press should wait on.
  • Ignore TLS certificate errors exists for LAN gear with a self-signed certificate. Leave it off for anything on the internet — turning it on there defeats the point of TLS.

UDP and TCP have no delivery guarantee​

A UDP action sends one datagram and forgets it — nothing tells you it arrived. A TCP action opens a fresh connection, sends, optionally reads one reply, and closes; it does not keep a session open. For gear that needs a persistent or streaming connection, these one-shot transports are the wrong fit. The socket transports are the newest part of the driver, so validate any UDP/TCP control on the actual hardware during commissioning rather than assuming it from a bench test.

Auto-revert timers do not survive a reboot​

A pending auto-revert countdown is dropped on a reboot — the control comes back in its restored (or forced) state with no timer running. This is deliberate parity with the previous driver. Two more things worth knowing:

  • Saving config from the setup app cancels every pending countdown. The state indices a timer was armed against may no longer mean the same thing after an edit, so the driver clears them.
  • Revert chains can loop. Nothing stops you configuring On → Off and Off → On; the app hints at it rather than forbidding it, so check a chain does what you intend.

The activity log is in memory​

The Activity tab holds roughly the last 100 calls and is cleared on a reboot. It is a commissioning and debugging aid, not a permanent audit trail. Nothing is written to disk, and no request log is kept — deliberately, since a request log would eventually hold a secret.

Webhook URLs are secrets​

The webhook token is carried in the URL, so a webhook URL is a credential. Keep it out of anything public, and regenerate the token (Webhooks tab) if one leaks — remembering that regenerating invalidates every URL you have handed out.

Everything is gated on the licence​

An unlicensed driver shows its tile but does nothing: presses, programming actions and inbound webhooks are all inert until a valid licence is active. A licensed site comes back from a reboot licensed on its own — you do not have to re-run the wizard after a power cut.

The setup app and the driver version together​

The setup app ships inside the driver package, so it always matches the driver and works on a site with no outbound internet. The flip side: updating the setup app means updating the driver. Importing a new driver package refreshes the app automatically.

Coexistence during changeover​

The new and previous UI Dynamic drivers can be installed side by side while you migrate a site — they are different drivers. See Migrating from the previous driver.